Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1261

reference
649-tree-1
name
1261
tree-preservation-order

undefined

649-tpo-1
uprn
address-text
point
POINT (-1.000237 50.863865)
geometry
MULTIPOLYGON (((-1.000180 50.863859,-1.000182 50.863870,-1.000190 50.863880,-1.000203 50.863888,-1.000218 50.863893,-1.000236 50.863895,-1.000253 50.863894,-1.000269 50.863889,-1.000282 50.863881,-1.000290 50.863871,-1.000293 50.863860,-1.000291 50.863849,-1.000283 50.863838,-1.000271 50.863830,-1.000255 50.863825,-1.000237 50.863823,-1.000220 50.863825,-1.000204 50.863830,-1.000191 50.863838,-1.000183 50.863848,-1.000180 50.863859)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL